1.84.0 release post #1451
1.84.0 release post #1451
Conversation
|
cc rust-lang/rust#133210 @lcnr @rust-lang/types -- I expanded/reworded a bit the stub you had started for new trait solver in coherence, would definitely appreciate review to make sure I didn't get the details too wrong :) cc @joshtriplett @rust-lang/cargo for the section on MSRV-aware resolver, I sort of semi-randomly came up with recommendations and general prose but very happy to replace it if there's something better or actual recommendations the team wants to offer :) cc @rust-lang/opsem for the strict provenance section -- I tried to find a balance between copying in the whole contents of the standard library docs and referencing them, very open to changes though. |
|
cc @rust-lang/release as well... |
|
cc @alex-semenyuk @traviscross for relnotes blog post (I am triagebot) |
|
@Mark-Simulacrum I already spent some effort on Strict Provenance release notes in rust-lang/rust#131996, did you see that? I thought that is the intended place for such text. |
|
cc @epage |
Co-authored-by: Weihang Lo <[email protected]>
Co-authored-by: Josh Triplett <[email protected]>
Co-authored-by: Josh Triplett <[email protected]>
Co-authored-by: Josh Triplett <[email protected]>
Thanks, I had seen it previously but missed it when putting together the blog (just my bad). Copied that text in, it looks good to me, thanks for writing it up! |
posts/2025-01-09-Rust-1.84.0.md
Outdated
|
|
||
| ## What's in 1.84.0 stable | ||
|
|
||
| ### Cargo can use toolchain version for library version selection |
There was a problem hiding this comment.
“A toolchain”? “The toolchain”?
There was a problem hiding this comment.
This header isn't ideal IMO -- but I'm not sure adding an article will help. It's hard for me to succinctly describe what this feature is without using jargon (e.g., MSRV), especially since it's not on by default.
Co-authored-by: Jake Goulding <[email protected]>
Co-authored-by: Travis Cross <[email protected]>
Co-authored-by: Ed Page <[email protected]>
Co-authored-by: alexey semenyuk <[email protected]>
|
OK, I think that incorporates the feedback I have clear solutions for. I'm still not super happy with the header for the MSRV section, but I don't have any better ideas than the tweak I applied just now. |
Co-authored-by: Ed Page <[email protected]>
Co-authored-by: lcnr <[email protected]>
|
|
||
| ### Strict provenance APIs | ||
|
|
||
| In Rust, [pointers are not simply an "integer" or |
There was a problem hiding this comment.
Should we also mention that provenance is also a thing C, for the sake of completeness and openness?
| In Rust, [pointers are not simply an "integer" or | |
| In Rust, as well as in C[^n3005], [pointers are not simply an "integer" or |
| detect and diagnose pointer misuse. | ||
|
|
||
| For more details, see the standard library [documentation on provenance](https://doc.rust-lang.org/std/ptr/index.html#provenance). | ||
|
|
There was a problem hiding this comment.
| [^n3005]: https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3005.pdf | |
Rendered